Skip to content

Conversation

@michaelnebel
Copy link
Contributor

@michaelnebel michaelnebel commented Nov 28, 2025

Instead of crashing the dependency fetcher in case dotnet --info gets killed (exit code 143), it is just reported as a warning.

@hvitved : I am all open for other suggestions as this is not ideal.

@github-actions github-actions bot added the C# label Nov 28, 2025
@michaelnebel michaelnebel changed the title C#: Gracefully handle non-zero exitcodes for dotnet --info. C#: Do not crash on dotnet --info failure. Nov 28, 2025
@michaelnebel michaelnebel force-pushed the csharp/nocrashdotnetinfo branch from e425d75 to af64e33 Compare November 28, 2025 13:44
@michaelnebel michaelnebel changed the title C#: Do not crash on dotnet --info failure. C#: Gracefully handle dotnet --info exit code 143. Nov 28, 2025
@michaelnebel michaelnebel requested a review from hvitved November 28, 2025 14:38
Copy link
Contributor

@hvitved hvitved left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What happens to the subsequent dotnet restore invocations, presumably those also fail with the same exit code?

@michaelnebel
Copy link
Contributor Author

What happens to the subsequent dotnet restore invocations, presumably those also fail with the same exit code?

No, they don't appear to be affected (for the current run, the restore fails with exit code 1 for the restore - but that is due to another issue, which I have a fix for).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants